Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove /gardens #426

Closed
wants to merge 1 commit into from
Closed

Remove /gardens #426

wants to merge 1 commit into from

Conversation

Corantin
Copy link
Contributor

We want app.gardens.fund to point directly to the /gardens and not to the landing page anymore.
The landing page wil leave in a long living branch for now so its easier to update it

Copy link

vercel bot commented Sep 12, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
gardens-v2 🔄 Building (Inspect) Visit Preview 💬 Add feedback Sep 12, 2024 7:45pm

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's perfectly fine! It means the code you were reviewing might:
  • Be focused on areas you didn't analyze: Maybe the changes were in helper functions, documentation, or tests, which you were intentionally skipping.
  • Be already well-structured: The code might already be designed with security and logic in mind, leaving little room for improvement in those areas.
  • Not have any significant logic changes: The changes could be purely cosmetic, like refactoring or renaming, without affecting the core logic.

What to do next:

  • Communicate clearly: Inform the developers that you focused your review on logic and security-sensitive areas and didn't find anything requiring your input.
  • Consider other aspects: If you have the time and expertise, you could offer to review for other aspects like readability, performance, or adherence to coding standards.
  • Don't force feedback: If there's genuinely nothing to comment on within your scope, it's better to avoid giving generic or unnecessary feedback.

Remember, a code review is a collaborative process. Clear communication about your focus and findings ensures everyone is on the same page.

</details>

@Corantin Corantin closed this Sep 12, 2024
@Corantin Corantin deleted the remove-gardens-route-prefix branch September 21, 2024 18:09
@Corantin Corantin restored the remove-gardens-route-prefix branch September 21, 2024 18:10
@Corantin Corantin deleted the remove-gardens-route-prefix branch September 26, 2024 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant